Docs mention --tracing.otlp.http=true flag but it is not accepted

[geigerzaehler]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?

I ran Traefik with the --tracing.otlp.http=true flag as suggested in the docs and it failed to start.

docker run --rm -p 8080:80 traefik:v3.0 --log.level=DEBUG --tracing.otlp.http=true

In fact, I initially came across this bug when I used the helm chart which can add this flag. I get a similar issue when using --tracing.otlp.grpc=true.

What did you see instead?

Traefik immediately exited with the following error

{"level":"error","error":"command traefik error: failed to decode configuration from flags: http cannot be a standalone element (type *types.OtelHTTP)","time":"2024-05-15T09:58:49Z","message":"Command error"}

What version of Traefik are you using?

Version: 3.0.0
Codename: beaufort
Go version: go1.22.2
Built: 2024-04-29T14:25:59Z
OS/Arch: linux/amd64

What is your environment & configuration?

no config

If applicable, please paste the log output in DEBUG level

No response

[ldez]

Hello,

the option depends on another option that is required: https://doc.traefik.io/traefik/observability/metrics/opentelemetry/#endpoint

[geigerzaehler]

When I add the option you linked to (--metrics.otlp.http.endpoint=http://localhost:4318/v1/metrics) I get the same error.

In any case, my issue wasn’t that I did not get OpenTemeletry to work but that the documentation mentions options that are not accepted by traefik which led to a downstream bug in the helm chart.

[nmengin]

Hello @geigerzaehler,

Thank you for reaching out.
Indeed, there is an issue in the configuration management we will fix.

[traefiker]

Closed by #10729.